home *** CD-ROM | disk | FTP | other *** search
-
- NATIONAL SEMICONDUCTOR CORPORATION
-
- "TROPIC" TokenRing NDIS Device Driver
-
-
-
- The NSC Tropic Tokenring adapter is a standard ISA BUS 16 bit network card
- compatible with Tokenring topology networks. The Driver is designed to operate
- under Microsoft LANMAN 2.1 for OS2 1.3 and DOS 5.0 operating systems.
- IBM Lan Server running under OS2 2.0 as well as Microsoft Windows for Workgroups
- is also supported. These notes cover certain details of operation for building the
- source code as well as installing and using the driver software on the above
- mentioned systems.
-
-
- Source build notes:
- -------------------
-
- Source code for the driver is included for those developers interested in
- modification for their own purposes or to see how a driver is structured
- for the Tropic Tokenring architecture.
-
- BAT and CMD files are included to build the NSCTOK driver. These command
- files set the environment variables used by the MAKEFILE. The standard
- Microsoft Toolkit files are assumed for building the driver.
-
-
- ENVIRONMENT VARIABLES:
-
- INCLUDE - Include file path
- LIB - Library file path
- TARGETOS - Target Operating System (DOS | OS2)
- VERSION - Version being built (PRODUCT | DEV)
- LISTINGS - Listing control (YES | NO)
-
- (Note, the DEV version conditional assembly statements have been removed,
- as development has been completed, PRODUCT is now the only version
- produced during the make.)
-
-
- COMMAND FILES
-
- MKALL - Makes both OS2 and DOS versions for both DEV and PRODUCT
- MKDOS - Makes DOS (accepts DEV or PRODUCT as command line argument)
- MKOS2 - Makes OS2 (accepts DEV or PRODUCT as command line argument)
-
- * All builds should be run from this directory.
-
-
-
- Installation Disk Notes:
- ------------------------
-
- OS2 and DOS DIRECTORY CONTENTS
-
- There are three different directory structures on the disk with the contents
- needed for each of the operating systems Lan manager products. The autosetup
- features of each Lan management product will work with the installation disk.
- When the Lan Management installation procedure prompts for the user setup
- disk, insert the NSC Tropic Installation disk and proceed as requested.
-
- Lanman.dos = The directory for DOS 5.0.
- Lanman.os2 = The directory for Microsoft OS2 1.3
- IBMLAN = The directory for IBM OS2 2.0 Lan Server.
-
- All these directorys contain the special NIF Files and a sample of
- the Protocol.ini files needed to install the driver for each system.
-
- Windows for Workgroups is supported by the OEMSETUP.INF file in the root
- of the install disk, as well as the PROTOCOL.INI fragment and the actual
- driver itself; NSCTOK.DOS.
-
- OPERATIONAL COMMENTS: DOS
-
- The NSC Tropic Token Ring adapter and driver have been tested with
- several EMS Memory management programs. QEMM works fine in that
- it will detect if a Token Ring style adapter of any type is in the system
- and will not relocate the shared memory segment. (Nice feature...)
- Microsoft's own EMM386 needs the shared memory area excluded with
- the x = parameter set accordingly or else the adapter and driver will not
- operate. Qualitas likewise requires an exclusion parameter set. These
- last two memory managers do not detect automatically as does QEMM. See
- the user manual for the proper procedure to exclude the shared memory
- space of the driver. Default shared memory area is D800 Hex.
-
- OPERATIONAL COMMENTS: OS2
-
- The OS2 2.0 Lan Server product from IBM does not currently support the
- automatic installation feature for an external vendor device driver disk.
- For OS2 2.0 IBM Lan Server installations, the user should manually move the
- files needed to the proper locations. Additionally, the config.sys and
- protocol.ini files will need to be edited to reflect the correct information
- for the NSC driver. The procedure to install is as follows:
-
- 1. Install any driver from the selection list (IBMTOK works fine).
-
- 2. Reboot after the Lan Server is installed under OS2.
-
- 3. Copy the NSCTOK.OS2 driver from the IBMLAN directory of the Tropic
- installation disk to the IBMCOM\MACS directory that was created
- during the IBM Lan Server installation process.
-
- 4. Copy the NSCTOK.NIF file from the IBMLAN directory of the Tropic
- installation disk to the IBMCOM\MACS directory.
-
- 5. Edit the Config.sys file to reflect the name of the NSC TROPIC
- device driver in the section that calls out the lan adapter
- driver in the Lan Server declaration statements. For example,
- if the driver installed initially was the IBM Token Ring driver
- the following line should be changed:
-
- DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 (original line)
-
- DEVICE=C:\IBMCOM\MACS\NSCTOK.OS2 (modified line)
-
- 6. Edit the Protocol.ini file in the IBMCOM directory to include the
- information for NSCTOK as listed in the IBMLAN directory of the
- NSC Tropic TokenRing installation disk. The Protocol.ini sample
- there has the typical default information.
-
- 7. Reboot the system with the new Tropic Tokenring card installed
- and everything should bind up and run correctly with the NSC card.
-
-